close
Skip to content

Vercel Connect for AI apps and agents

Read the docs
$npm install @vercel/connect
Securely connect agents to the tools, data, and services they need to take action.
Install the skill
$ npx skills add vercel/vercel-plugin --skill vercel-connect
Connect to Slack
Via CLIVercel Dashboard(opens in new tab)
$ vercel connect create slack --name acme-slack
Use its data in agents(opens in new tab) and apps(opens in new tab)
import { getToken } from '@vercel/connect';


const token = await getToken('slack/acme-slack');
Read the docs
  • Secure credentials for agent workflowsUse short-lived, scoped tokens instead of long-lived secrets. Keep access controlled across projects and environments.
  • Request credentials at runtimeCreate and manage connectors from Vercel, then request credentials when your app or agent needs them.
  • Built for agents that take actionConnect agents to services like Slack, GitHub, and Notion so they can read context and trigger workflows.
  • Centralized connection managementManage all third-party connections in one place across your team, projects, and environments.

Get started

See Vercel Connect in action with one of our templates.

Read the docs
Software FactoryShip a software factory that puts AI agents on every stage of the development loop.
Marketing TeamDeploy an entire marketing team of agents orchestrated from Slack for social, SEO, email, and more.
Personal AgentA personal agent that works with you day-to-day in Slack, GitHub, and Linear.

Frequently asked questions

What is Vercel Connect?
Vercel Connect lets your agents and services access external systems on behalf of your users and teams. Instead of storing provider credentials in long-lived environment variables, you request user-authorized tokens at runtime with project-level access controls.
What problem does Vercel Connect solve?
It removes long-lived third-party secrets from your runtime while still letting agents act on external APIs. You register a connector for a provider, link it to projects and environments, request provider tokens at runtime, and keep an audit trail of authorization and token usage.
How does Vercel Connect work?
Connect uses a connector model. A connector is a registered third-party connection your team can reuse, and an installation is a provider-side install for a specific tenant, such as a Slack workspace or GitHub organization. At runtime you make a token request — optionally scoped with an installation, scopes, resources, and authorization details — bound to specific projects and environments.
Which connectors are available?
Connect supports generic OAuth and API Key connectors, plus dedicated connectors for Slack, GitHub, Linear, Discord, Notion, Salesforce, Figma, Snowflake, and WorkOS. Resend, Workday, Microsoft Teams and more are coming soon.
When should I use Vercel Connect instead of Integrations?
Use Vercel Integrations for marketplace-managed installs and provider-managed products in the Vercel Marketplace. Use Vercel Connect when you need delegated runtime credentials and user authorization for agent workflows — for example, an agent that needs project-scoped access to a Slack workspace.
How does pricing work?
Pricing is based on token requests and triggers forwarded. The Hobby plan includes 500 token requests and 1,000 trigger forwards at no additional cost. On the Pro plan, token requests are billed at $3.00 per 1,000 token requests and trigger forwards are billed at $0.95 per 1,000 forwards. Enterprise is billed at your negotiated Enterprise rate. Contact your account team for details.
Does Vercel Connect support webhook triggers?
Yes. Webhook trigger forwarding is currently Slack-only. When enabled, Connect can forward incoming Slack webhooks to up to three destination projects per connector.